Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#1029: Extended trivy rego for Kernel CVE's #1031

Merged
merged 2 commits into from
Dec 5, 2024

Conversation

tomuben
Copy link
Collaborator

@tomuben tomuben commented Dec 5, 2024

fixes #1029

All Submissions:

  • Check if your pull request goes to the correct bash branch (develop or master)?
  • Is the title of the Pull Request correct?
  • Is the title of the corresponding issue correct?
  • Have you updated the changelog?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • Are you mentioning the issue which this PullRequest fixes ("Fixes...")

When integrating to Develop branch:

  1. Remember to merge with "Squash and Merge"

When integrating to Main branch:

  1. Remember to merge with "Merge"
  2. Have you thought about version number? If there is a breaking change in the toolchain, need to update major version.
  3. If you plan a release, have you checked the Exasol packages for updates?
    1. Websocket API (https://github.com/EXASOL/websocket-api)
    2. Exasol-BucketFS

@tomuben tomuben changed the title Security/1029 extend trivy kernel ignore regex #1029: Extended trivy rego for Kernel CVE's Dec 5, 2024
@tomuben tomuben merged commit 154f465 into develop Dec 5, 2024
12 checks passed
@tomuben tomuben deleted the security/1029_extend_trivy_kernel_ignore_regex branch December 5, 2024 15:20
tomuben added a commit that referenced this pull request Dec 5, 2024
Changelog:
- Update version to 9.1.0 (#1030) 
- #1029: Extended trivy rego for Kernel CVE's (#1031)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants